Profile management method

ABSTRACT

Most computer operating systems are able to automatically configure the coupled computer peripheral device for use with the computer operating system without the need for installation of a specific driver. However, when these peripheral devices are detected by the computing system, a generic UI control configuration is often assigned to them and whatever customised settings previously configured by the user will be lost and replaced with a new set of unfamiliar setting. This poses much inconvenience and hassle to gamers when they use a different computing system or machine. Described according to an embodiment of the invention is a profile management method, operating on a computing cloud, comprising steps for receiving client data provided by a computing system detecting coupling of a user-interface (UI) thereto and for retrieving configuration data corresponding to the client data for use in configuring the UI by the computing system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit of U.S.application Ser. No. 12/959,707 having a filing date of Dec. 3, 2010,which is expressly incorporated by reference herein in its entirety.

FIELD OF INVENTION

The present invention relates generally to peripheral devices forcomputing systems. In particular, the invention relates to a system andmethod for managing the profile of peripheral devices foruser-interfaces of computing systems.

BACKGROUND

In most computer games, speed and accuracy are often of significantimportance to gamers. Familiarity with gaming control configurationswill therefore determine how one performs in the game. Typically,frequent gamers have a specific set of customised device configurationsuniquely suited for their game play. For example, to initiate a punch orto engage a weapon, gamers are able to re-assign combinations of keys onthe keyboard or on the mouse to initiate different UI control. Gamersoften do not break away from this set of configuration as it allows themfamiliarity and hence speed and control during gaming.

Some of these gamers are even equipped with their own preferredperipheral devices. Computer peripheral devices include but are notlimited to computer mice, keyboards, handheld gaming consoles andjoysticks. Known computer peripheral devices are typicallyinterchangeable and can be used with different computer systems andplatforms. Most computer operating systems are able to automaticallyconfigure the coupled computer peripheral device for use with thecomputer operating system without the need for installation of aspecific driver. However, when these peripheral devices are detected bythe computing system, a generic UI control configuration is oftenassigned to them and whatever customised settings previously configuredby the user will be lost and replaced with default settings. This posesmuch inconvenience and hassle to garners when they enter LAN-gamingshops or utilise computers for their gaming pleasures as they would haveto reconfigure the control settings to suit their preferences.

There is, therefore, an apparent need for a method whereby these devicesettings and configurations can be stored and retrieved on the fly sothat users can do away with the hassle of re-configuring their controlsettings whenever they use a different platform to access the differentperipheral devices.

SUMMARY

In accordance with a first aspect of the invention, there is disclosed aprofile management method comprising receiving client data provided by acomputing system, with the client data comprising device data beingdescriptive of a user-interface (UI) in signal communication with thecomputing system, and associating one of a plurality of device profileswith the device data, each of the plurality of device profiles havingconfiguration data associated therewith. The device data is furtherdescriptive of the user interactions identifiable by the UI. The profilemanagement system further comprises providing the configuration dataassociated with the one of the plurality of device profiles to thecomputing system for configuring operation of the UI with the computingsystem therewith.

In accordance with a second aspect of the invention, there is discloseda profile management system comprising a controller module for receivingclient data provided by a computing system. The client data comprisesdevice data being descriptive of a user-interface (UI) in signalcommunication with the computing system. The device data is furtherdescriptive of the user interactions identifiable by the UI. The profilemanagement system further comprises a storage module having storedthereon a plurality of device profiles, each of the plurality of deviceprofiles having configuration data associated therewith, and a processormodule for associating one of a plurality of device profiles stored onthe storage module with the device data. The configuration dataassociated with the one of the plurality of device profiles isprovidable by the controller module to the computing system forconfiguring operation of the UI with the computing system therewith.

In accordance with a third aspect of the invention, there is disclosed amachine readable medium having stored therein a plurality of programminginstructions, which when executed, the instructions cause the machineto: receive client data provided by a computing system, the client datacomprising device data being descriptive of a user-interface (UI) insignal communication with the computing system, the device data beingfurther descriptive of the user interactions identifiable by the UI;associate one of a plurality of device profiles with the device data,each of the plurality of device profiles having configuration dataassociated therewith; and provide the configuration data associated withthe one of the plurality of device profiles to the computing system forconfiguring operation of the UI with the computing system therewith.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system diagram of a profile management system residing ona computing cloud according to an exemplary embodiment of the invention;

FIG. 2 shows a system diagram of the profile management system of FIG. 1with user-interfaces in signal communication with computing systemscoupled thereto;

FIG. 3 shows a process flow diagram of a profile management method forimplementation by the collaboration management system of FIG. 1;

FIG. 4 shows a process flow diagram of a device discovery method forimplementation by the computing systems of FIG. 2; and

FIG. 5 shows an arrangement of device profile, configuration data, useridentifier and authentication data residing on the profile managementsystem of FIG. 1.

DETAILED DESCRIPTION

Reference will now be made in detail to an exemplary embodiment of thepresent invention, examples of which are illustrated in the accompanyingdrawings. While the invention will be described in conjunction with theembodiment, it will be understood that they are not intended to limitthe invention to these embodiments. On the contrary, the invention isintended to cover alternatives, modifications and equivalents, which maybe included within the spirit and scope of the invention as defined bythe appended claims. Furthermore, in the following detailed descriptionof embodiments of the present invention, numerous specific details areset forth in order to provide a thorough understanding of the presentinvention. However, it will be recognized by one of ordinary skill inthe art that the present invention may be practiced without thesespecific details. In other instances, well-known methods, procedures,components, and circuits have not been described in detail as not tounnecessarily obscure aspects of the embodiments of the presentinvention.

For purposes of brevity and clarity, descriptions of embodiments of thepresent invention are limited hereinafter to the transfer and managementof device profiles, in particular, device configurations, to clientdevice associated with the computing system. This however does notpreclude embodiments of the invention where fundamental principalsprevalent among the various embodiments of the invention such asoperational, functional or performance characteristics are required.

An exemplary embodiment of the invention, a profile management method100, is described hereinafter. The profile management method 100 ispreferably for managing configuration of user interfaces (UI) 18 coupledto computing system 20 in communication with a computing cloud 22.Further described, with reference to FIGS. 1 to 6, is a profilemanagement system 24, residing on the computing cloud 22, for applyingthe profile management method 100.

Generally, the profile management system 24 enables a configuration forUIs 18 to be created by a user so that the configuration can be readilyaccessed from different locations or from different computer terminalswhen the same or similar type of UI 18 is used. For example, when a usercarries a personal mouse from location to location, the user does nothave to reconfigure the mouse at each new location or at a new computerterminal. The configuration for the UI 18, including the preferredsettings therefor, are downloadable via the computer terminal the UI 18is coupled to. This even applies to newly acquired devices where the UI18 thereof can be configured for use “out of the box” via downloadingthe corresponding configuration previously created by a user, a thirdparty, the device manufacturer or an application developer, for example,a gaming application. The configurations for the UIs 18 are preferablystored on one or more servers with each configuration catering to aspecific, or similar, UI type and relating to a specific user identifiedby a user identifier. Download of the configuration can be initiated viavarious means including by the coupling of the UI 18 to a computersystem, connecting to a specific network address, for example an IPaddress or a URL, launching of a particular application or gameapplication or through operating of controls within an application.Preferably, information on the UI type is providable to the one or moreserver so that the configuration corresponding to the UI type, andpreferably further corresponding to a particular user ID, can beidentified for download and subsequent configuration of thecorresponding UI 18.

With reference to FIGS. 1 to 5, the computing cloud 22 comprises one ormultiple server systems 26 inter-networked and configured to function asthe profile management system 24. Communication pathway between thecomputing cloud 22 and the computing system 20 is preferably providedvia a local area network (LAN), a wide area network (WAN), the Internet,cellular networks, data networks, dedicated networks or a combination ofany thereof.

The profile management system 24 comprises a controller module 28 forreceiving client data 29 provided by the computing system 20, a storagemodule 30 for storing a plurality of device profiles 31 and a processormodule 32. The client data 29 comprises device data 34 for associatingwith one of the plurality of the device profiles 31 by the processormodule 32.

The profile management method 100 comprises a step 102 of receiving theclient data 29 providable by the computing system 20 by the profilemanagement system 24, a step 104 of associating one of the plurality ofdevice profiles 31 within the profile management system 24 with theclient data 29 and a step 106 of providing configuration data 36associated with one of the plurality of device profiles 31 to thecomputing system 20 for configuration of the UI 18 thereafter.

The device data 34 is preferably descriptive of the UI 18 associatedwith the computing system 20. The device data 34 is further descriptiveof the user interactions identifiable by the UI 18. Preferably, the UI18 is one of a computer peripheral coupled with an interface formedintegral with the computing device. Examples of computer peripheralsinclude but are not limited to gaming console, joystick, computer mouse,keyboard and speakers. Alternatively, the UI 18 includes devices whichare connectable for use with or forms part of the computing system 20,for example, the touch screen display of a cell phone or a smart phonewith the non-UI portions of the cell phone or smart phone forming thecomputing system 20. The UI 18 is preferably at least one of actuation,for example mouse button actuation or key presses, touch, light, sound,motion and position sensing. Detection and recognition of the UI 18, orits functional equivalent, occurs when the UI 18 is in signalcommunication with the computing system 20. The computing system 20generates the device data 34 for the UI 18 when the UI 18 is recognisedthereby. For example, if the UI 18 is a 3D mouse, the user interactionsidentifiable by the 3D mouse would include free-space movement orposition, scrolling actions and actuation of specific buttons existingon the 3D mouse. However, if the UI 18 is a multi-touch interface, theuser interactions identifiable by the multi-touch interface wouldinclude locations of one or more points and gestures generatable by theone or more touch points on the multi-touch interface. Therefore, theuser interactions identifiable and hence the device data when the UI 18is a 3D mouse differs from when the UI 18 is a multi-touch interface.

When a user couples the UI 18 to the computing system 20 in networkcommunication to the computing cloud 22, the profile management system24 is able to receive the client data 29 generated by the computingsystem 20. The UI 18 may be connected to the computing system 20 viawired or wireless signal connection. Detection of the UI 18 can beconfigured by the user to be in response to coupling of the UI 18 to thecomputing system 20 or to be effected by the user by executing a routineor application on the computing system. Application programminginterfaces (APIs) or components of software development kits (SDKs) ispreferably made available for programmers, game developers andapplication developers to incorporate the function of detecting the UI18 onto their computing systems 20 and software applications. This willprovide the user with better control over how and when the UI 18 is tobe detected for discovery and sending of the client data 29 to theprofile management system 24. The APIs and components of SDKs may beprovided for development of auto-executable routines residing on the UI18 for initiating the profile management method 100 upon detectionthereof by the computing system 20 when the UI 18 is coupled thereto. Insuch an instance, the device data 34 specific to the UI 18 may bepre-defined and preloaded onto the UI 18, preferably, onto a memorymodule residing on the UI 18.

Preferably, the client data 29 further comprises identifier data 38uniquely matched to at least one of a plurality of user identifiers 40residing on the storage module 30. Upon receiving of the client data 29by the profile management system 24 in the step 102, the profilemanagement system 24 further processes the client data 29 for eitheruser registration or log-on to the profile management system 24. For anexisting user with an identity existing as one of the plurality of useridentifiers 40 on the storage module 30, access to the profilemanagement system 24 triggers the processor module 32 to associate theparticular one of the user identifiers 40 with the identifier data 38.Upon associating the one of the user identifiers 40 with the identifierdata 38, the one of the device profiles 31 and the configuration data 36corresponding thereto are consequently identified. As an alternativeover the identifier data 38 or in the absence of the identifier data 38,the device data 34 may be used for identifying the corresponding one ofthe device profiles 31 and the corresponding configuration data 36. Inan event where none of the device profiles 31 exactly matches the devicedata 38, a closest matching one of the device profiles 31 may beselected instead. The controller module 28 can be configured to select aclosest matching one of all the device profiles 31 on the storage module30 or a closest matching one of only the device profiles 31 associatedwith a particular one of the user identifiers 40.

In an example of use of the profile management system 24, a user coupleshis multi-touch device, the UI 18, to a public computer, the computingsystem 20. One or both of the multi-touch device and the public computermay be pre-loaded with a sub-routine to automatically connect to theprofile management system 24 for initiating the profile managementmethod 100. Alternatively, the user can manually connect with theprofile management system 24, for example, via a URL using a webbrowser. Once the profile management method 100 has been initiated, themulti-touch device will send information, the client data 19, to theprofile management system 24 indicating that it is of a multi-touchdevice type, the device data 34. The sent information can include theuser's name or a user identifier, the identifier data 38. On the profilemanagement system 24, the user identifier 40 matching with the user'sname may have multiple device profiles 31 associated therewith, forexample various types of devices including a 3-D mouse, a specific modelof gaming mouse and a multi-touch device. With the sent informationindicating that the multi-touch device is of a multi-touch device type,the profile management system 24 can isolate the corresponding one ofthe multiple device profiles 31 for extracting the configuration data 36corresponding 36 thereto. The configuration data 36 can include, for themulti-touch device, a library of gestures and corresponding instructionsfor download to the public computer for configuring use of themulti-touch device with the public computer. Upon the multi-touch devicebeing configured with the public computer, the user can immediatelyinteract with the multi-touch device to generate instructions withgestures the user is familiar with without having to redefine gesturesand corresponding instructions.

In another example of use of the profile management system 24, themulti-touch device is a newly acquired device connectable to the profilemanagement system 24, via the user's personal computer, the computingsystem 20, for locating and downloading a popular gesture library or alibrary of gesture provided by the manufacturers of the multi-touchdevice, the configuration data 36 for use in configuring the multi-touchdevice with the user's personal computer. In yet another example of useof the profile management system 24, the UI 18 is a gaming mouse for usewith a public computer, the computing system 20. A user with hispreferred settings, the configuration data 36, stored on the profilemanagement system 24 is able to connect the public computer to theprofile management system 24 for downloading the configuration data 36to the public computer. The configuration data for the gaming mousecould include one or more of button configuration, scroll-wheel andmouse displacement sensitivity and lighting or haptic feedback responseto the gaming mouse. The availability of the configuration data 36 onthe profile management system 24 allows the user to quickly configurethe gaming mouse, or other UIs 18, when using the public computer.

For retrieval of configuration data 36 from the profile managementsystem 24 in the step 104, the user may either log-on to the profilemanagement system 24 to retrieve stored configuration data 36 accessibleto the public or choose to retrieve device data previously uploaded tothe profile management system 24 associated with the user identifier 40belonging to the user. Download of the configuration data 36 by otherusers is preferably determined by permission settings associated withthe configuration data 36. Upon receiving client data 29 by thecontroller module 28, the profile management system 24 may initiateautomated download of the configuration data 36 associated with thedevice profile 31 matching with the device data 34 of the providedclient data 29 in the step 106.

Preferably, the step 102 of receiving client data 29 comprises a step108 of receiving authentication information (unreferenced) from thecomputing system 20, for example a password provided by a user, toauthenticate the identifier data 34 using the authentication data 42corresponding thereto. Preferably, the profile management system 24 isconfigured such that the configuration data 36 in association with theidentified one of the device profiles 31 will only be provided by thecontroller module 28 to the computing system 20 in the step 106 when theidentifier data 34 is authenticated. Preferably, the configuration data36 substantially defines interactions between the UI 18 and at least oneof an application and an operating platform operating on the computingsystem 20. In gaming applications, the configuration data 36 can be asingle or a permutation of a plurality of keys on the keyboard for gamecontrol such as to engage a weapon or to cast a spell. In non-gamingapplications, configuration data can include voice activated commands orgestures to manipulate UI 18 on touch interfaces.

When there exists a mismatch of operating platforms supported by thecomputing system 20 and which the stored configuration data operates on,the step 106 comprises a step 112 of processing the configuration data36 for compliance with an operating platform so that the configurationdata 36 downloadable from the profile management system 24 can becorrectly recognised and configured for operation of the UI 18 with thecomputing system 20. The operating platform is definable by platformdata (unreferenced) constituting a portion of the client data 29generatable by the computing system 20 for provision to the profilemanagement system 24.

Complementary to and in association with the profile management method100, there exists a device discovery method 116 configurable by the userfor edited of data on the profile management system 24. The devicediscovery method 116 is preferably applied by the computing system 20.The device discovery method 116 comprises a step 124 of providing clientdata 29 for log-on to the profile management system 24 and a step 126 ofuploading the device data 34 to the profile management system 24.

The step 124 further comprises at least one of a step 132 for detectingcoupling of the UI 18 to the computing system 20, a step 134 formanually keying in of identifier data 38 to effect log-on to the profilemanagement system 24 and a step 136 for registering a new useridentifier 40 with the profile management system 24. Preferably in thestep 132, the computing system 20 detects signal communication of the UI18 with and generates the client data to effect an automated log-on tothe profile management system 24 by associating the identifier data 38with one of the device profiles 31. Alternatively, the user mayconfigure settings of the device discovery method 116 such that a log-onprompt will be initiated for requesting provision of the identifier data38 upon the computing system 20 detecting signal communication of the UI18 therewith. The user will then be required to manually key-in theidentifier data 38 in the step 134 for access to the profile managementsystem 24. In the step 136, a new user may register with the profilemanagement system 24 by following through with a registration process.The registration process may request the new user to either manuallykey-in new identifier data 38 to be stored on the storage module 30 asone of the user identifiers 40 or couple a new device to the computingsystem 20 for extraction of the identifier data 38 therefrom.

In the step 126, a user may define and upload new client data 24 ontothe storage module 30 in the profile management system 24 under one ofthe user identifiers 40. The device data 34 in association with theclient data 29 will be stored in the profile management system 24 as oneof the device profiles 31. The configuration data 36 for new UI settingsand configuration will also be uploaded for storage by the profilemanagement system 24 and will be registered as being associated with thenewly created one of the device profiles 31. Preferably, the profilemanagement system 24 allows for subsequent editing of the configurationdata 36 after being uploaded to the storage module 30.

In the gaming context, for gamers who are always on the move, theirpreferred settings configurations for computer peripherals, eithergeneral settings or game-specific settings, are made storable andaccessible through a multitude of devices and platforms. In LAN-gamingshops or at any public access terminal, garners have their preferredsettings configurations on the fly and downloadable via the profilemanagement system 24 to any terminal or platform in networkcommunication thereto. Users with new gaming devices can also utilisethe profile management system 24 to obtain a set of basic settingconfiguration for the UI 18 without having to manually configure controlfor any possible manipulation of the UI 18. Update or modification ofsetting configurations from any computing system 20 in networkcommunication with the profile management system 24 is also an availableoption.

Additionally, the profile management system 24 is able to process usageinformation and data stored in the storage module 30 for a variety ofapplications, including data analytics, and for access by users or thirdparties. The storage module 30 is preferably accessible by a thirdparty. The third party includes, for example, a games developer, anadvertiser or a network service provider. In addition, knowledge of theconfiguration preferences of users, in particular garners, will enablegame developers to design products that will better satisfy consumers.

In a non-gaming context, for example, when a user connects a multi-touchscreen smart phone to profile management system 24 on the computingcloud 22, or when voice command memos are being downloaded from the cellphone to the computing system 20 , configurations previously stored inthe smart phone for manipulation of the UI 18 as well as specific voiceactivated commands used previously in the cell phone can be downloadedfrom the profile management system 24 and thereby be used with thecomputing system 20, having the various commands or controls mimickedseamlessly.

The profile management method 100 preferably resides on the profilemanagement system 24 as a plurality of instructions stored on a machinereadable medium of the profile management system 24. It is preferredthat the instructions, when executed, cause the profile managementsystem 24 to perform the step of the profile management method 100.Similarly, the device discovery method 116 exists on the computingsystem 20 as a plurality of instructions stored on a machine readablemedium thereof. It is preferred that the instructions, when executed,cause the profile management system 24 to perform at least one of thesteps of the device discovery method 116.

In a forgoing manner, a profile management method 100 and profilemanagement system 24 are described according to exemplary embodiments ofthe invention. Although only a number of embodiments of the inventionare disclosed in this document, it will be apparent to one skilled inthe art in view of this disclosure that numerous changes and/ormodifications can be made to the disclosed embodiments without departingfrom the scope and spirit of the invention.

The following examples pertain to further embodiments.

Example 1 is a profile management method comprising: receiving clientdata provided by a computing system, the client data comprising devicedata being descriptive of a user-interface (UI) in signal communicationwith the computing system, the device data being further descriptive ofthe user interactions identifiable by the UI; associating one of aplurality of device profiles with the device data, each of the pluralityof device profiles having configuration data associated therewith; andproviding the configuration data associated with the one of theplurality of device profiles to the computing system for configuringoperation of the UI with the computing system in response to at least aportion of the user interactions identifiable by the UI.

In example 2, the subject matter of example 1 can optionally includethat the UI is one of a computer peripheral coupled with an interfaceformed integral with the computing device.

In example 3, the subject matter of example 1 can optionally includethat the UI is at least one of actuation, touch, light, sound, motionand position sensing.

In example 4, the subject matter of example 1 can optionally includethat the client data further comprises identifier data being indicativeof the user interactions being identifiable by the UI.

In example 5, the subject matter of example 4 can optionally includethat associating one of a plurality of device profiles with the devicedata comprises: associating one of a plurality of user identifiers withthe identifier data, each of the plurality of identifier data having atleast one of the plurality of device profiles associated therewith; andassociating the device data with one of the plurality of device profilesassociated with the one of the plurality of user identifiers associatedwith the identifier data.

In example 6, the subject matter of example 4 can optionally includereceiving authentication data from the computing system; andauthenticating the identifier data using the authentication data,wherein the configuration data is provided to the computing system inresponse to the identifier data being authenticated.

In example 7, the subject matter of example 1 can optionally includethat the configuration data substantially defines interactions betweenthe UI and at least one of an application and an operating platformoperating on the computing system.

In example 8, the subject matter of example 1 can optionally includethat providing the configuration data associated with the one of theplurality of device profiles to the computing system comprises:processing the configuration data for compliance with an operatingplatform, the client data comprising a platform data describing theoperating platform.

Example 9 is a profile management system comprising: a controller modulefor receiving client data provided by a computing system, the clientdata comprising device data being descriptive of a user-interface (UI)in signal communication with the computing system, the device data beingfurther descriptive of the user interactions identifiable by the UI; astorage module having stored thereon a plurality of device profiles,each of the plurality of device profiles having configuration dataassociated therewith; a processor module for associating one of aplurality of device profiles stored on the storage module with thedevice data, wherein the configuration data associated with the one ofthe plurality of device profiles is providable by the controller moduleto the computing system for configuring operation of the UI with thecomputing system in response to at least a portion of the userinteractions identifiable by the UI.

In example 10, the subject matter of example 9 can optionally includethat the UI is one of a computer peripheral coupled with an interfaceformed integral with the computing device.

In example 11, the subject matter of example 10 can optionally includethat the UI is at least one of actuation, touch, light, sound, motionand position sensing.

In example 12, the subject matter of example 9 can optionally includethat the client data further comprises identifier data being indicativeof the user interactions being identifiable by the UI.

In example 13, the subject matter of example 12 can optionally includethat the processor module is further configured to associate one of aplurality of user identifiers with the identifier data, each of theplurality of identifier data having at least one of the plurality ofdevice profiles associated therewith; and associating the device datawith one of the plurality of device profiles associated with the one ofthe plurality of user identifiers associated with the identifier data.

In example 14, the subject matter of example 12 can optionally includean authentication module for receiving authentication data from thecomputing system; and authenticating the identifier data using theauthentication data, wherein the configuration data is provided to thecomputing system in response to the identifier data being authenticated.

In example 15, the subject matter of example 9 can optionally includethat the configuration data substantially defines interactions betweenthe UI and at least one of an application and an operating platformoperating on the computing system.

In example 16, the subject matter of example 9 can optionally includethat the processor module is further configured to process theconfiguration data for compliance with an operating platform, the clientdata comprising a platform data describing the operating platform.

Example 17 is a machine readable medium having stored therein aplurality of programming instructions, which when executed, theinstructions cause the machine to: receive client data provided by acomputing system, the client data comprising device data beingdescriptive of a user-interface (UI) in signal communication with thecomputing system, the device data being further descriptive of the userinteractions identifiable by the UI; associate one of a plurality ofdevice profiles with the device data, each of the plurality of deviceprofiles having configuration data associated therewith; and provide theconfiguration data associated with the one of the plurality of deviceprofiles to the computing system for configuring operation of the UIwith the computing system in response to at least a portion of the userinteractions identifiable by the UI.

In example 18, the subject matter of example 17 can optionally includethat the UI is one of a computer peripheral coupled with and aninterface formed integral with the computing device.

In example 19, the subject matter of example 17 can optionally includethat the UI is at least one of actuation, touch, light, sound, motionand position sensing.

In example 20, the subject matter of example 17 can optionally includethat the client data further comprises identifier data being indicativeof the user interactions being identifiable by the UI.

In example 21, the subject matter of example 20 can optionally includethat the plurality of programming instructions, when executed, cause themachine to: associate one of a plurality of device profiles with thedevice data comprising: associate one of a plurality of user identifierswith the identifier data, each of the plurality of identifier datahaving at least one of the plurality of device profiles associatedtherewith; and associate the device data with one of the plurality ofdevice profiles associated with the one of the plurality of useridentifiers associated with the identifier data.

In example 22, the subject matter of example 20 can optionally includereceiving authentication data from the computing system; andauthenticating the identifier data using the authentication data,wherein the configuration data is provided to the computing system inresponse to the identifier data being authenticated.

In example 23, the subject matter of example 17 can optionally includethat the configuration data substantially defines interactions betweenthe UI and at least one of an application and an operating platformoperating on the computing system.

In example 24, the subject matter of example 17 can optionally includethat the plurality of programming instructions, when executed, cause themachine to: process the configuration data for compliance with anoperating platform, the client data comprising a platform datadescribing the operating platform.

1. A user-interface device at least one of connectable for use with orforms part of a computing system, the user-interface device comprising:a sensor configured to identify user interactions by sensing at leastone of actuation, touch, light, sound, motion or position; a memorymodule pre-loaded with a sub-routine and a device data; wherein thesub-routine is configured to connect to a computing cloud through thecomputing system; wherein the user-interface device is configured totransmit the device data to the computing cloud, the device data beingdescriptive of the user interactions identifiable by the sensor; whereinan operation of the user-interface device with the computing system isconfigurable using a configuration data of a plurality of configurationdata downloadable from the computing cloud, the configuration data beingassociated with the device data.
 2. The user-interface device of claim1, wherein each configuration data of the plurality of configurationdata is associated with a device profile of a plurality of deviceprofiles.
 3. The user-interface device of claim 1, wherein the devicedata is associated with a respective device profile of the plurality ofdevice profiles.
 4. The user-interface device of claim 3, wherein eachdevice profile of the plurality of device profiles is associated with atleast one configuration data of the plurality of configuration data. 5.The user-interface device of claim 4, wherein the configuration dataassociated with the device data is the configuration data associatedwith the device profile associated with the device data.
 6. Theuser-interface device of claim 1, wherein the sub-routine is configuredto automatically connect to the computing cloud.
 7. The user-interfacedevice of claim 1, wherein the sub-routine is configured to connect tothe computing cloud in response to receiving a user input.
 8. Theuser-interface device of claim 1, wherein the configuration data atleast substantially defines interactions between the user-interfacedevice and at least one of an application or an operating platformoperating on the computing system.
 9. The user-interface device of claim1, wherein the configuration data defines interaction between at leastone of a single key on the user-interface device or a permutation of aplurality of keys on the user-interface device, and an applicationoperating on the computing system.
 10. The user-interface device ofclaim 1, wherein the configuration data comprises at least one of voiceactivated commands or gestures for manipulating the user-interfacedevice.
 11. The user-interface device of claim 1, wherein theconfiguration data comprises a library of gestures and correspondinginstructions for configuring an operation of the user-interface device.12. The user-interface device of claim 1, wherein the configuration datacomprises at least one of a button configuration, a scroll-wheelsensitivity, a displacement sensitivity, a lighting feedback or a hapticfeedback.
 13. The user-interface device of claim 1, wherein theuser-interface device is configured to transmit a client data to thecomputing cloud, the client data comprising information for logging ontothe computing cloud.
 14. The user-interface device of claim 13, whereinthe client data comprises an identifier data associable with at leastone user identifier of a plurality of user identifiers residing on thecomputing cloud.
 15. The user-interface device of claim 14, wherein eachuser identifier of the plurality of user identifiers correspond to atleast one of a device profile or a configuration data stored in thecomputing cloud.
 16. The user-interface device of claim 13, wherein theclient data is stored in the memory module.
 17. The user-interfacedevice of claim 1, wherein the user-interface device is configured to bedetectable by the computing system.
 18. The user-interface device ofclaim 17, wherein the user-interface device is detectable in response toone of coupling of the user-interface device to the computing system orexecution of an application on the computing system.
 19. Theuser-interface device of claim 1, further comprising a coupling memberconfigured to provide one of a wired connection or a wirelessconnection, to couple to the computing system.
 20. The user-interfacedevice of claim 1, wherein the user-interface device is a computerperipheral device.
 21. The user-interface device of claim 1, wherein theuser-interface device is one from the group consisting of a gamingconsole, a joystick, a computer mouse, a keyboard and a speaker.
 22. Theuser-interface device of claim 1, wherein the user-interface device isone of a 3D mouse or a multi-touch interface device.
 23. A computingsystem comprising: a detection module configured to detect coupling witha user-interface device; a communication module configured to establishcommunication with a computing cloud; a generator module configured togenerate a device data when the user-interface device is recognisedthereby; wherein the device data comprises description of theuser-interface device and information on user interactions identifiableby the user-interface device; wherein the computing system is configuredto provide a client data comprising the device data, to the computingcloud, wherein the computing system is further configured to downloadfrom the computing cloud, a configuration data of a plurality ofconfiguration data associated with the client data; wherein thecomputing system is further configured to configure operation of theuser-interface device in response to user interactions identifiable bythe user-interface device, based on the downloaded configuration data.24. The computing system of claim 23, configured to establishcommunication with the user-interface device via at least one of wiredcommunication or wireless communication.
 25. The computing system ofclaim 23, wherein the detection module is configured to detect couplingof the user-interface device upon execution of an application on thecomputing system.
 26. The computing system of claim 23, pre-loaded witha sub-routine configured to connect to the computing cloud.
 27. Thecomputing system of claim 26, wherein the sub-routine is configured toautomatically connect to the computing cloud.
 28. The computing systemof claim 26, wherein the sub-routine is configured to connect to thecomputing cloud in response to receiving a user input.
 29. The computingsystem of claim 23, wherein the configuration data at leastsubstantially defines interactions between the user-interface device andat least one of an application or an operating platform operating on thecomputing system.
 30. The computing system of claim 23, wherein theconfiguration data defines interaction between at least one of a singlekey on the user-interface device or a permutation of a plurality of keyson the user-interface device, and an application operating on thecomputing system.
 31. The computing system of claim 23, wherein theconfiguration data comprises at least one of voice activated commands orgestures for manipulating the user-interface device.
 32. The computingsystem of claim 23, wherein the configuration data comprises a libraryof gestures and corresponding instructions for configuring an operationof the user-interface device.
 33. The computing system of claim 23,wherein the configuration data comprises at least one of a buttonconfiguration, a scroll-wheel sensitivity, a displacement sensitivity, alighting feedback or a haptic feedback.
 34. The computing system ofclaim 23, wherein each configuration data of the plurality ofconfiguration data is associated with a device profile of a plurality ofdevice profiles.
 35. The computing system of claim 23, wherein thedevice data is associated with a respective device profile of theplurality of device profiles.
 36. The computing system of claim 35,wherein each device profile of the plurality of device profiles isassociated with at least one configuration data of the plurality ofconfiguration data.
 37. The computing system of claim 36, wherein theconfiguration data associated with the client data is the configurationdata associated with the device profile associated with the device data.38. The computing system of claim 23, wherein the client data comprisesinformation for logging onto the computing cloud.
 39. The computingsystem of claim 23, wherein the client data comprises an identifier dataassociable with at least one user identifier of a plurality of useridentifiers residing on the computing cloud.
 40. The computing system ofclaim 39, wherein each user identifier of the plurality of useridentifiers corresponds to at least one of a device profile of aplurality of device profiles stored on the computing cloud or aconfiguration data of a plurality of configuration data stored on thecomputing cloud.
 41. The computing system of claim 40, wherein eachdevice profile of the plurality of device profiles is associated with atleast a configuration data of the plurality of configuration data. 42.The computing system of claim 23, further comprising the user-interfacedevice.
 43. The computing system of claim 23, wherein the client datacomprises a platform data describing an operating platform supported bythe computing system.